<html>
<head><meta charset="utf-8"><title>critical-ops · t-release · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/index.html">t-release</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html">critical-ops</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="243203553"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243203553" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> XAMPPRocky <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243203553">(Jun 18 2021 at 20:11)</a>:</h4>
<p>Sorry for the late reply, this discussion does have me thinking, if there are some low effort ways we can improve communication around critical issues.</p>
<p>What would people think about a <code>#critical-ops</code> (or w/e name) stream where you could safely <code>@everyone</code> to alert in the channel about critical issues?</p>
<p>The messages could just link to the discussion in another stream or to the GitHub comment, but it would provide people a separate bucket that they can make sure they get alerted on.</p>



<a name="243204271"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243204271" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243204271">(Jun 18 2021 at 20:20)</a>:</h4>
<p>Hm. Can you say more about what "critical issues" are? If you mean P-critical, I don't think that's a good interpretation of the meaning -- they don't really mean that all hands need to be fixing or caring about them, just that we aim to have a resolution by the associated release (ideally via the milestone).</p>



<a name="243204768"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243204768" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> XAMPPRocky <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243204768">(Jun 18 2021 at 20:24)</a>:</h4>
<p>I don’t think the intention is to have all hands on deck, but it allows people to see what’s going on at very high level even if they’re not a part of fixing it.</p>
<p>Because I know for some GitHub’s notifications are still pretty overwhelming and it can be easier to miss.</p>
<p>Just speaking for myself I get no GitHub notifications outside of me deliberately choosing to go to the website or app, but I get Zulip notifications on my phone.</p>



<a name="243205750"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243205750" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243205750">(Jun 18 2021 at 20:34)</a>:</h4>
<p>Sure, but -- I guess -- what would your goal be with having P-critical notify you? From my perspective, T-release members shouldn't need to know until late in the cycle -- T-compiler is in charge of the implementation/fixing. Weekly reports, though, on progress and status might help -- but to be honest from my perspective it's really hard to gauge whether something will happen</p>



<a name="243207338"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243207338" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> XAMPPRocky <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243207338">(Jun 18 2021 at 20:52)</a>:</h4>
<p>Well personally I think information should be shared as soon as possible even if it’s not considered actionable yet, it’s easier to take action when you’re already caught up with the situation.</p>
<p>I also just think there’s inherent value in having a dedicated release-ops to collect this information in one place. Easier to spend 5 minutes every couple days reading one stream, then spending a half hour reading through a long GitHub thread to understand the context.</p>



<a name="243207556"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243207556" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243207556">(Jun 18 2021 at 20:55)</a>:</h4>
<p>We can feed issues labeled automatically into a stream, but it's a lot of work to prepare summaries and information on a regular basis</p>



<a name="243208318"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243208318" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> cuviper <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243208318">(Jun 18 2021 at 21:04)</a>:</h4>
<p><span class="user-mention silent" data-user-id="116122">simulacrum</span> <a href="#narrow/stream/241545-t-release/topic/critical-ops/near/243205750">said</a>:</p>
<blockquote>
<p>From my perspective, T-release members shouldn't need to know until late in the cycle -- T-compiler is in charge of the implementation/fixing.</p>
</blockquote>
<p>I do see T-release as having a responsibility to shepherd issues for beta/stable, even though we don't own the development work</p>



<a name="243208874"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243208874" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> XAMPPRocky <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243208874">(Jun 18 2021 at 21:11)</a>:</h4>
<p>I don’t really see a high value in creating new summary reports, I imagined it more as a place for “in-flight” updates or in a “as it happens” format.</p>



<a name="243209519"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243209519" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243209519">(Jun 18 2021 at 21:20)</a>:</h4>
<p>Discussions or updates don't currently really happen on any regular basis outside T-compiler meetings though; I'm not sure what updates to the channel would be provided (or who would create them).</p>



<a name="243209682"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243209682" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243209682">(Jun 18 2021 at 21:23)</a>:</h4>
<p>If we want to run through all issues during each T-release meeting, that could work</p>



<a name="243209877"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243209877" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> cuviper <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243209877">(Jun 18 2021 at 21:25)</a>:</h4>
<p>let's try that -- we can refine if that feels too tedious/burdensome</p>



<a name="243210221"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243210221" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243210221">(Jun 18 2021 at 21:30)</a>:</h4>
<p>Do you want to own that project in terms of leading those discussion(s) going forward?</p>



<a name="243210320"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243210320" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> XAMPPRocky <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243210320">(Jun 18 2021 at 21:32)</a>:</h4>
<p><a href="/user_uploads/4715/Ij7qu2TP_0dVcS0aazbbEgHf/C04CE145-2DB8-40FE-97C7-49D30F6B78FE.jpg">C04CE145-2DB8-40FE-97C7-49D30F6B78FE.jpg</a></p>
<div class="message_inline_image"><a href="/user_uploads/4715/Ij7qu2TP_0dVcS0aazbbEgHf/C04CE145-2DB8-40FE-97C7-49D30F6B78FE.jpg" title="C04CE145-2DB8-40FE-97C7-49D30F6B78FE.jpg"><img src="/user_uploads/4715/Ij7qu2TP_0dVcS0aazbbEgHf/C04CE145-2DB8-40FE-97C7-49D30F6B78FE.jpg"></a></div>



<a name="243210335"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243210335" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> XAMPPRocky <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243210335">(Jun 18 2021 at 21:32)</a>:</h4>
<p>Hmm I meant to post a message with that but the Zulip app deleted it.</p>



<a name="243210387"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243210387" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> XAMPPRocky <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243210387">(Jun 18 2021 at 21:33)</a>:</h4>
<p><span class="user-mention" data-user-id="116122">@simulacrum</span> I think just linking to where in the meetings the discussion happened would be a big improvement, as someone not in regular attendance the compiler meeting stream can be very busy.</p>



<a name="243210442"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243210442" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243210442">(Jun 18 2021 at 21:34)</a>:</h4>
<p>A good portion of each meeting is about backports and regressions -- in fact, it's rare that anything else really gets discussion time.</p>



<a name="243210456"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243210456" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243210456">(Jun 18 2021 at 21:34)</a>:</h4>
<p>But I am still not fully connecting whether considerable value can be derived from those discussions</p>



<a name="243210635"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243210635" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> XAMPPRocky <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243210635">(Jun 18 2021 at 21:37)</a>:</h4>
<p>Sure but not all regressions are equally impactful as something like the incr comp issues.</p>



<a name="243210725"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243210725" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> cuviper <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243210725">(Jun 18 2021 at 21:38)</a>:</h4>
<p><span class="user-mention" data-user-id="116122">@simulacrum</span> you have your hands in so many things that I don't expect you will get much value at all. <span aria-label="wink" class="emoji emoji-1f609" role="img" title="wink">:wink:</span></p>



<a name="243210766"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243210766" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> cuviper <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243210766">(Jun 18 2021 at 21:39)</a>:</h4>
<p>I can own that part of the meeting</p>



<a name="243210890"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243210890" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> cuviper <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243210890">(Jun 18 2021 at 21:41)</a>:</h4>
<p>I think the goal for T-release is not even discussion most of the time, just checking status</p>



<a name="243210897"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243210897" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243210897">(Jun 18 2021 at 21:41)</a>:</h4>
<p>I was trying to extrapolate to others to be clear. I am subscribed to rust-lang/rust globally, and try to skim each thread at a high level, so I definitely don't think I would derive much value -- but if we think there is value for others, that might be helpful.</p>



<a name="243210923"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243210923" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> cuviper <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243210923">(Jun 18 2021 at 21:41)</a>:</h4>
<p>basically triage, but with higher priority and visibility</p>



<a name="243210989"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243210989" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> cuviper <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243210989">(Jun 18 2021 at 21:42)</a>:</h4>
<p>(I don't know how you drink from that fire hose!)</p>



<a name="243210998"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243210998" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243210998">(Jun 18 2021 at 21:43)</a>:</h4>
<p>I think part of it is that I think the status on most P-critical issues goes from no activity (80% of time open) -&gt; PR (10% of time) -&gt; Closed (10% of time) in the happy path, with obviously some +/- on that, but generally this is not actionable at any point without being able to coordinate engineering resources, IMO.</p>



<a name="243211011"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243211011" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243211011">(Jun 18 2021 at 21:43)</a>:</h4>
<p>(Which, obviously, realistically none of us have the ability to do).</p>



<a name="243211127"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243211127" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> cuviper <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243211127">(Jun 18 2021 at 21:44)</a>:</h4>
<p>if P-critical means release-blocking, we need to have some influence</p>



<a name="243211160"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243211160" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243211160">(Jun 18 2021 at 21:45)</a>:</h4>
<p>The problem is "over who" :)</p>



<a name="243211163"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243211163" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> cuviper <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243211163">(Jun 18 2021 at 21:45)</a>:</h4>
<p>from polite nagging, to asking other team leads, as the situation may fit</p>



<a name="243211195"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243211195" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243211195">(Jun 18 2021 at 21:46)</a>:</h4>
<p>Like, to some extent, that happens naturally through T-compiler meetings. I think we can add atop of that, perhaps, but I'm not sure that it will be of much help.</p>



<a name="243211583"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243211583" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> cuviper <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243211583">(Jun 18 2021 at 21:51)</a>:</h4>
<p>our part might just be a summary, "here's what T-compiler (or whoever) is saying"</p>



<a name="243211592"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243211592" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> XAMPPRocky <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243211592">(Jun 18 2021 at 21:51)</a>:</h4>
<p>I would also hope that this stream would have value for non-team members to help out when possible.</p>
<p>For example, in the early stages of a new regression when there’s no MCVE currently available for the issue. Or help with testing a fix in nightly in their production code. Things that anyone could do, but don’t really have a channel to communicate those tasks.</p>



<a name="243211651"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243211651" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243211651">(Jun 18 2021 at 21:52)</a>:</h4>
<p>We do! Or, at least, that part is potentially much easier.</p>



<a name="243211687"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243211687" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243211687">(Jun 18 2021 at 21:53)</a>:</h4>
<p>@rustbot ping cleanup or similar pings a whole bunch of people specifically interested in helping with that kind of work</p>



<a name="243211724"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243211724" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243211724">(Jun 18 2021 at 21:53)</a>:</h4>
<p>Creating a stream on Zulip for such issues would be pretty easy.</p>



<a name="243212085"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243212085" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> XAMPPRocky <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243212085">(Jun 18 2021 at 21:59)</a>:</h4>
<p>Yeah, having a stream with pings like that is kinda what I’m after. The problem I have with groups is it requires deciding to opt into the group, which is not a visible concept in Zulip really, and it might give people impression that they’re signing up to do it forever, or at least repeatedly which is maybe not what they can do.</p>



<a name="243212145"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243212145" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243212145">(Jun 18 2021 at 21:59)</a>:</h4>
<p>(To be clear, no such groups on Zulip exist today; we only have the triagebot lists controlled via the team repo)</p>



<a name="243212211"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243212211" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243212211">(Jun 18 2021 at 22:00)</a>:</h4>
<p>But forwarding ping groups to streams / topics here on Zulip would be easy; the code is basically all written, just a few connecting lines need drawing.</p>



<a name="243212234"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243212234" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> XAMPPRocky <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243212234">(Jun 18 2021 at 22:00)</a>:</h4>
<p>Is that not the same thing, I thought the triagebot lists were Zulip groups?</p>



<a name="243212283"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243212283" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> XAMPPRocky <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243212283">(Jun 18 2021 at 22:01)</a>:</h4>
<p>Oh right @rustbot is only on GitHub.</p>



<a name="243212559"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243212559" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243212559">(Jun 18 2021 at 22:04)</a>:</h4>
<p>no, triagebot doesn't know anything about zulip groups</p>



<a name="243835609"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243835609" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> pnkfelix <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243835609">(Jun 24 2021 at 19:35)</a>:</h4>
<p><span class="user-mention silent" data-user-id="116122">simulacrum</span> <a href="#narrow/stream/241545-t-release/topic/critical-ops/near/243212211">said</a>:</p>
<blockquote>
<p>But forwarding ping groups to streams / topics here on Zulip would be easy; the code is basically all written, just a few connecting lines need drawing.</p>
</blockquote>
<p>This sounds like an interesting idea. The supposed benefits are, IIUC: 1. zulip is better ingrated with mobile devices than github for some contributors, and 2. zulip is better than github for ad-hoc discussion in response to a live ping... Does that sounds right?</p>



<a name="243836903"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/critical-ops/near/243836903" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> XAMPPRocky <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/critical-ops.html#243836903">(Jun 24 2021 at 19:45)</a>:</h4>
<p>Yeah, Zulip notifications are more managable for myself, so they are louder and easier to reach me. I could get GitHub notifications to my phone (and do use the mobile app), but enabling push notifications would be enabling dozens notifications a day (nearly all of which I don't need or want to handle immediately). There's no way fine grained way currently to be like "only give notifications for the project board in <code>rust-lang/rust</code>"  in Github at the moment.</p>
<p>Where as on Zulip that can be accomplished by just having a stream.</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>